Underground/Underground CD1.iso/hack/progsy/mailbomb/alanch35/ADDON.TXT

Text File | 1997-08-26 | 14.2 KB | 342 lines

╔════════════════════════════════════════════════════════════════════════════╗
║░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║
╚════════════════════════════════════════════════════════════════════════════╝

                              Avalanche V3.5
                Addon Implementation Documentation Revision 3

                    Avalanche Copyright 1996-1997 H-Master


No parts of this document can be replicated, without the WRITTEN consent of
the copyright holder, for uses other than the promotion / distribution of this
software.


╔════════════════════════════════════════════════════════════════════════════╗
║░░  Contents  ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║
╚════════════════════════════════════════════════════════════════════════════╝

        Contents
        Introduction
        How it works
        Format of Avalanche mail bomber session save files
        Format of Avalanche mailing lists subscriber session save files
        Limitations/Warnings
        Some ideas
        Contact Information


╔════════════════════════════════════════════════════════════════════════════╗
║░░  Introduction  ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║
╚════════════════════════════════════════════════════════════════════════════╝

        Sometimes, no matter how good a program is, it can be better.
        However, to add new features is usually a long and tedious process
        because ultimately, there is only one or a group of people working on
        the program.  Therefore, addons were invented.  Addons allow other
        programmers to program features for a program without actually seeing
        the code of the program.  This is through the use of a form of
        communication between the program and the addon that will alter or
        refine the way the program works.  In order to make Avalanche the best
        e-mail bomber there is, I have added some addon functionality, through
        the use of the Avalanche save session feature.


╔════════════════════════════════════════════════════════════════════════════╗
║░░  How it works  ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║
╚════════════════════════════════════════════════════════════════════════════╝

        Here's how addons work.  First of all, to use an addon, you will have
        to save the current session.  Then, you will start the addon and point
        it to the save file.  Then, when the addon has finished with the save
        file, you exit the addon, go back to Avalanche and load the new
        editted save file.


╔════════════════════════════════════════════════════════════════════════════╗
║░░  Format of Avalanche mail bomber session save files  ░░░░░░░░░░░░░░░░░░░░║
╚════════════════════════════════════════════════════════════════════════════╝

        This section is only for people who are interested in making addons or
        wish to manually alter the mail bomber session save files.

        The format of the save file is as follows:

        Avalanche Mail Bomber Save Session Format: <Format Number>
        <Flags><Relays>|<Number of e-mails>|<Number of mass mailings>
        <File attachment>
        <Domain name>
        <To>
        <Sender's name>
        <From>
        <Server>
        <Subject>
        <E-Mailer>
        <Number of carbon copies>
        <Carbon copies>
        <Number of custom headers>
        <Custom headers>
        <Message>

        Whereby:
        <Format Number> is the "version" for the saved session file's format.
        You should check this before performing any actions on the file.

        <Flags> are a list of integer specifying options.  The flags are:

        1. Use mass mailing                   (1 if true, 0 if false)
        2. Use random insult for subject      (1 if true, 0 if false)
        3. Append random insult to message    (1 if true, 0 if false)
        4. Request Notification               (1 if true, 0 if false)
        5. Use real IP for mail headers       (1 if true, 0 if false)
        6. Use number of e-mails              (1 if true, 0 if false)
        7. Spasm/Epileptic mode         (0 = normal, 1 = spasm, 2 = epileptic)
        8. Priority   (0 = highest, 1 = high, 2 = normal, 3 = low, 4 = lowest)

        <Relays> refers to the number of relays
        <Number of e-mails> refers to the number of e-mails to send.  This
                            number is meaningless if flag 6 is 0 (I.E: Send
                            forever).
        <Number of mass mailings> refers to the number of times to use mass
                                  mailing.

        E.G of line 2:
        1000010211|1000|10

        Means:
        use mass mailing
        not to use random insult in subject
        not to append insult to message
        not to request for notifications
        not to use IP for mail headers
        use number of e-mails to determine number of e-mails to send
        send e-mails in normal mode
        send e-mails with normal priority
        use 11 relays
        send 1000 e-mails in total
        use 10 mass mailings

        Note that the pipe (|) is used to seperate the numbers that may be
        more than one digit long.

        <File attachment> refers to the FULL PATH NAME to the file that is to
                          be attached with the e-mails.  This is to be left
                          blank if no file is to be sent (I.E: Use a blank
                          line).

        E.G of line 3:
        c:\alanche\insult.lst

        <Domain name> refers to the fake domain name.  This is to be left
                      blank if none is specified.

        E.G of line 4:
        www.h-master.com

        <To> refers to the victim of the bombing.  This is to be left blank if
             no one is specified.

        E.G of line 5:
        [e-mail]

        <Sender name> refers to the name of the sender.  This is to be left
                      blank if no one is specified.

        E.G of line 6:
        A dork

        <From> refers to the e-mail address of the person where the mails are
               supposed to come from.  This is meaningless if flag 3 = 1.
               This is to be left blank if no one is specified.

        E.G of line 7:
        [e-mail]

        <Server> refers to the primary server to use for the bombing.  This
                 is to be left blank if none is specified.

        E.G of line 8:
        aol.com

        <Subject> refers to the subject of the message.  This is meaningless
                  if flag 2 = 1.  This is to be left blank if none is
                  specified.

        E.G of line 9:
        Get a life

        <E-Mailer> refers to the e-mailer information to use.  This is to be
                   left blank if none is specified.

        E.G of line 10:
        Avalanche 2.8 (16)

        <Number of carbon copies> refers to the number of people in the carbon
                                  copy list.  For every person in the carbon
                                  copy list, there will be an additional line
                                  to the save file, with the e-mail address of
                                  the person.

        E.G of line 11:
        3

        <Carbon copies> refers to the people in the carbon copy list.  Each
                        seperate e-mail address will be on a new line.  This
                        is to be left blank if <Number of carbon copies> = 0.

        E.G of lines until the number of carbon copies is reached:
        [e-mail]
        [e-mail]
        [e-mail]

        <Number of custom headers> refers to the number of custom headers
                                   there are.  For every line in the custom
                                   headers list, there will be an additional
                                   line to the save file, with the header.

        E.G of the line after <Carbon copies>:
        3

        <Custom headers> refers to the headers in the custom headers list.
                         This is to be left blank if <Number of custom
                         headers> = 0.

        E.G of lines until the number of custom headers is reached:
        Reply-To: [e-mail]
        X-LSV-ListID: Avalanche
        X-ASPMail-Registered-To: Nobody

        <Message> refers to the message body of the e-mails.  This is to be
                  left blank if not specified.

        E.G of lines after <Custom headers> until the end of the file:
        Hello 1
        Hello 2


╔════════════════════════════════════════════════════════════════════════════╗
║░░  Format of Avalanche mailing lists subscriber session save files  ░░░░░░░║
╚════════════════════════════════════════════════════════════════════════════╝

        This section is only for people who are interested in making addons or
        wish to manually alter the mailing lists subscriber session save
        files.

        The format of the save file is as follows:

        Avalanche Mailing List Subscriber Save Session Format: <Format Number>
        <Domain name>
        <Victim's e-mail address>
        <Victim's name>
        <Server>
        <Name of mailing list server>
        <Mailing lists with flags>

        Whereby:
        <Format Number> is the "version" for the saved session file's format.
        You should check this before performing any actions on the file.

        <Domain name> refers to the fake domain name.  This is to be left
                      blank if none is specified.

        E.G of line 2:
        www.h-master.com

        <Victim's e-mail address> refers to the e-mail address of the victim.
                                  This is to be left blank if no one is
                                  specified.

        E.G of line 3:
        [e-mail]

        <Victim's name> refers to the name of the victim.  This is to be left
                        blank if no one is specified.

        E.G of line 4:
        Lame Dork

        <Server> refers to the primary server to use for the bombing.  This
                 is to be left blank if none is specified.

        E.G of line 5:
        aol.com

        <Name of mailing list server> refers to the name of the mailing list
                                      server as described in MAILING.LST or
                                      it's replacement.  This should NOT be
                                      left blank or the program may crash.

        E.G of line 6:
        Anthrax Edu. (LS)

        <Mailing lists with flags> refers to the mailing lists that are listed
                                   (after the listbox has been updated) and
                                   in front of each list is a number (1 or 0).
                                   If the number is 1, then the list is tagged
                                   and if the number is 0, the list is not
                                   tagged.  Note that there can be more than
                                   one mailing list.

        E.G of line 7 to the end of the file:
        1VBASIC-L
        0VC-L
        1DELPHI-L
        1PASCAL


╔════════════════════════════════════════════════════════════════════════════╗
║░░  Limitations/Warnings  ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║
╚════════════════════════════════════════════════════════════════════════════╝

        There are some limits that you need to take note of.  Exceeding the
        limits may result in Avalanche crashing or not working properly.

        1) Do not give a value for the flags that is outside the given range.
        2) The maximum number of relays is 30000.
        3) The maximum number of e-mails is 30000.
        4) The maximum number of characters in the carbon copy is 30000,
           including the 2 bytes used for <CR/LF>.
        5) The maximum number of characters in the message is 30000, including
           the 2 bytes used for <CR/LF>.


╔════════════════════════════════════════════════════════════════════════════╗
║░░  Some ideas  ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║
╚════════════════════════════════════════════════════════════════════════════╝

        This section is used to provide potential programmers some ideas on
        what types of addons can be made.  If you wish to add to this list,
        please contact me.  Contact information is below.

        1) Add in anonymous remailer support.  This can be done by changing
           the To: field to the e-mail address of the remailer and by editting
           the message body to provide the information required by the
           remailer.  Try making it such that the remailers can be chained.
        2) Add PGP support for the message.
        3) Use the lists that comes with Avalanche to randomize the servers,
           e-mailer, person to frame, etc.
        4) Use a save session as a template to create more save sessions that
           will be used to bomb other people.  This will allow for multiple
           Avalanche sessions to bomb.
        5) Use the message to implement new SMTP headers.
        6) Make a front end for Avalanche.
        7) Format/Spell check the message.


╔════════════════════════════════════════════════════════════════════════════╗
║░░  Contact Information  ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║
╚════════════════════════════════════════════════════════════════════════════╝

        If for some reason or another you wish to contact me, here's my info.

        IRC Nick     : H-Master
        IRC Network  : Galaxynet / EFnet / Dalnet (In order of perferences)
        E-mail       : [e-mail] (No flames / chains / bombs!)
        Homepage     : http://ted.org/~hmaster/ and
                       http://www.mintprimary.com/spear/hmaster/

        Note that if you tell me about your addon, I may add it to my page or
        if it is really very good, then I may include it in future releases of
        Avalanche.